HP Operations Manager for Windows

com.hp.openview.ib.api.jopc
Class JOpcException


java.lang.Object
  |
  +--java.lang.Throwable
		|
		+--java.lang.Exception
			|
			+--com.hp.openview.ib.api.jopc.JOpcException
All Implemented Interfaces:
java.io.Serializable

public class JOpcException
extends java.lang.Exception

Used for exception handling within the HPOM Java API classes. No public constructors - instances will be thrown by API only.


Method Summary
 java.lang.String getMessage()
          get the corresponding message of the exception reason
 JOpcException[] getNestedExceptions()
          Get nested exceptions.
 int getReason()
          get the reason of the exception
 java.lang.String getStack()
           
 
Methods inherited from class java.lang.Throwable
fillInStackTrace, getLocalizedMessage, printStackTrace, printStackTrace, printStackTrace, toString
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
 

Method Detail

getMessage

public java.lang.String getMessage()
get the corresponding message of the exception reason
Overrides:
getMessage in class java.lang.Throwable
Returns:
the message string

getReason

public int getReason()
get the reason of the exception
Returns:
the reason

getStack

public java.lang.String getStack()

getNestedExceptions

public JOpcException[] getNestedExceptions()
Get nested exceptions. This may occur for HPOM API operations on arrays of objects. Then the C API may return OPC_ERR_NOT_COMPLETELY_DONE and the individual objects have to asked for their status. To simplify this, the Java API generates individual exceptions for the offending objects which can be queried with this method. If the nested exceptions are of class JOpcObjException they also point to the offending objects - see JOpcObjException.getObject(). If there are no nested exception the method returns null.
Returns:
the array of nested exceptions.

 

500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.